Systems and methods for maintaining a workflow management system

ABSTRACT

Systems, methods, and devices are presented for providing and managing investments and workflow for investors and sponsors are described. The system provides and utilizes an actionable, reliable, transparent, real-time, collaborative marketplace for facilitating funding and distribution and for reviewing the performance of private placements via an online, authoritative, unified compliance and execution platform for private placements and other investments.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.16/578,218, filed Sep. 20, 2019, which is a continuation of U.S.application Ser. No. 15/206,152, filed Jul. 8, 2016, which claimspriority to U.S. Provisional Patent Application No. 62/191,104, filed onJul. 10, 2015, entitled UNIFIED COMPLIANCE AND EXECUTION PLATFORM FORPRIVATE PLACEMENTS, which are hereby incorporated by reference in theirentireties.

TECHNICAL FIELD

The present disclosure relates generally to systems, apparatuses, andcomputer-implemented methods for managing and generating data andbusiness process workflows, such as workflows associated with alternateinvestments.

BACKGROUND

Investments are assets purchased by users that, presumably, appreciatein value over a period of time, providing the users with returns (gains)to the assets. Example investment assets may include stocks, bonds,property, funds, other complex investment vehicles, and so on. Forexample, private placement investments involve the sale of securities toa relatively small number of select investors as a way of raisingcapital. Private placement investors are commonly large banks, mutualfunds, insurance companies, high-wealth investors, and pension funds.

Advantages of investing in private placements can include, for example,an ability to hire professional investment managers, which maypotentially be able to offer better returns and more adequate riskmanagement, the benefit of economies of scale (e.g., lower transactioncosts), and increased asset diversification to reduce systemic risk.Private placements are the opposite of a public issue, in whichsecurities are made available for sale on the open market and, as aconsequence, private placements are not required to be registered withthe Securities and Exchange Commission. In many cases, detailedfinancial information is not disclosed to investors, and in some cases,a prospectus is waived.

The potential benefits of private placements (e.g., hiring professionalfund managers, and so on) and the risks of being less regulated orunregulated by a central organization of repute have created uniqueproblems affecting efficient investment in private place investments,particularly for smaller private placements that may not have enoughresources, know-how, time, or savvy to privately organize, regulate, anddisseminate private fund information to a wide range and number ofinvestors, often of different types (e.g., mutual fund investor versushigh-wealth foreign individual investor), resulting in, e.g., lessinvestor confidence and inefficient market entrance and exit strategies.

In addition, information associated with other complex or opaqueinvestment vehicles may be difficult to provide to many investors,causing the investors and the managers of investments to miss out onmatching investments with suitable investors. In such cases,conventional mechanisms for managing transactions between parties (e.g.,hiring professional fund managers) and/or collecting and aggregatingdata underlying the transactions and associated processes generallysuffer from various drawbacks, such as inefficient or cumbersomeprocedures often performed with unrelated entities, administrators, anddocuments.

The need exists for a technology that overcomes the above problems, aswell as one that provides additional benefits. Overall, the examplesherein of some prior or related systems and their associated limitationsare intended to be illustrative and not exclusive. Other limitations ofexisting or prior systems will become apparent to those of skill in theart upon reading the following Detailed Description

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a basic and suitable computer that mayemploy aspects of the described technology.

FIG. 2 is a block diagram of a basic and suitable network and networkresources that may employ aspects of the described technology.

FIG. 3 is a block diagram of a unified compliance and execution platformfor private placements that employs aspects of the described technology.

FIG. 4A is an example user interface that is configured to allowsponsors and investors authorized access into an UCEP marketplace.

FIG. 4B is an example user interface for displaying various investorand/or sponsor characteristics.

FIG. 5 is an example user interface dashboard.

FIG. 6 is a strategy user interface.

FIGS. 7A-7H illustrate various embodiments for displaying investmentinformation.

FIGS. 8A-8G are example user interfaces that depict a profile userinterface.

FIGS. 9A-9B are example portfolio user interfaces.

FIG. 10 is an example vault user interface.

FIG. 11 is a flow diagram illustrating an example method for providing aprivate placement investment to an investor.

FIG. 12 is a flow diagram illustrating an example method for providing aprivate placement investment by a sponsor.

FIG. 13 is a block diagram illustrating various components of a unifiedinvestment management system.

FIG. 14 is a flow diagram illustrating a method for performing actionsassociated with one or more investments.

FIGS. 15A-15F are example user interfaces presented by the unifiedinvestment management system.

FIGS. 16A-16F are example user interfaces presented during completion ofa subscription of an investment.

FIGS. 17A-17C are additional example user interfaces presented by theunified investment management system.

FIGS. 18A-18B are example user interfaces associated with the contentsof a data vault provided by the unified investment management system.

DETAILED DESCRIPTION

Overview

Systems and methods for managing investments, such as presentingtargeted or specific information associated with alternativeinvestments, dynamically generating workflows based on investment data(e.g., resulting in documents representative of agreements betweenparties, documents completed for compliance purposes, and so on),facilitating the funding and disbursement of investments, and so on, aredescribed. The systems and methods may be part of, or provided by, aplatform supported by unified investment management system. The unifiedinvestment management system performs various actions to managedifferent types of alternative investments, such as private placementinvestments, fund-based investments (e.g., investments shared bymultiple investors and managed by an entity), and so on.

In some embodiments, the unified investment management system mayinclude a data structure component that generates, maintains, modifies,updates, and/or accesses a data structure containing one or moreentries, wherein each of the one of more entries is associated with aninvestment. For example, each entry of the data structure relatesinformation associated with an investment, such as an identifier for theinvestment, information representative of a fund associated with theinvestment, information representative of a user associated with theinvestment, and other information.

The system, therefore, may utilize the investment-tailored datastructure to perform various actions associated with managing andproviding investments on behalf of its users. For example, the systemmay include a request component that receives a request via a userinterface to display information associated with investments managed bythe unified investment management system, a query component that queriesthe investment-centric data structure to identify information associatedwith the investments managed by the unified investment management systemthat satisfies the received request, and an information component thatpresents the identified information that satisfies the received request.

In some embodiments, the system may apply various business logicalgorithms or operations to data retrieved from the data structure inorder to generate and/or augment workflows associated with theinvestments. For example, the system may inject the data into thealgorithms to calculate or otherwise determine various resultsassociated with a target workflow, such as a workflow associated withcapital statement generation, other document generation, compliancedocument generation, capital call commencement, and so on.

A workflow, in some embodiments, manages and administers processesassociated with investments and/or funds managed by the system. Aworkflow tracks and manages all steps or operations performed by thesystem associated with investments. Workflows generate records and otherdocuments, such as records used to provide compliance and auditinformation (e.g., to support audits, regulators, and so on), recordsused during transactions, and so on.

For example, a workflow may obtain data from the data structure relatingvarious data objects to an investment, perform various logic algorithms(e.g., capital management logic) utilizing the data (e.g., investorinformation and ownership percentages) to calculate, using the logic(e.g., a specific fee structure), to determine or calculate values(e.g., fees) to be provided in transactions, documents, and so on.

Therefore in some embodiments, the system utilizes an investmentspecific data structure, which includes entries that relate informationfor investments, in order to perform various actions associated withmanaging investments. Such a data structure, therefore, enables thesystem to perform various complex actions associated with processworkflows, such as workflows associated with managing private placementinvestments, workflows associated with rendering and displaying variousviews, profiles, or interfaces of information (e.g., fund interfaces,investor interfaces, and so on), workflows associated with managingsubscriptions of investments by investors, workflows associated withperforming compliance and other ancillary functions, and so on.

Further, the system, via the utilization of the specific datarelationships, enables transparent viewing and access of data,documents, meta data, audit records, and so on, to investors, fundmanagers, compliance officers, third parties, and so on. The system,therefore, may transparently exchange data and resulting records betweeninternal parties and/or external, third, parties, among other benefits.

Examples of Workflows Associated with Private Placement Investments

Although the system is described later herein, the following sectionprovides details regarding the use case of managing workflows forprivate placement investments using aspects of the systems describedherein.

The inventors have recognized that private placement investments oftenoperate based on a per-fund, per-investor, and/or per-industry basisfor, e.g., raising funds; disseminating investment information; locatingand qualifying investors; transferring funds; complying with state,federal, and international regulations; escrowing capital; distributinginvestment capital; reporting; and other investment concerns. Small tomidsize investment funds may not have enough time or money to createreliable back-end technology for managing private placement operations.Instead, sponsors may resort to time-consuming and inconvenient methodsof conducting business, such as mailing and/or emailing binders,prospectuses, questionnaires, and other investment data; conductingin-person or telephone conferences to discuss terms; and separatelyengaging accountants, lawyers, trustees, beneficiaries, escrow agents,etc. For a single fund, this manual and often unwieldy process can berepeated over and over for every prospective investor because not allinvestors of the same fund share the same terms, require execution ofthe same documents, and/or share the same capital accounts and transfermechanisms, for example. Sponsors of multiple funds may repeat thisentire process for each new fund.

Introduced below are methods, devices, and systems (collectively hereinreferred to as “technology”) related to providing and utilizing anactionable, reliable, transparent, real-time, collaborative marketplacefor facilitating funding and distribution and for reviewing theperformance of private placements via an online, authoritative, unifiedcompliance and execution platform (UCEP) for private placements. UCEP'smarketplace, in various embodiments, is industry-independent. Forexample, real estate developers, bond investors, energy investors, andother industries can independently and simultaneously leverage themarketplace, regardless of investor type, fund size, or objectives.

UCEP's authoritative online technology organizes, schedules, verifies,shares, notifies, and analyzes private placement operations (among otheroperations) without the back-and-forth, manual steps currently performedby sponsors and investors. In some embodiments, the technology providesa centralized “back office” for some or all private placement funds. Forexample, the UCEP marketplace provides enhanced risk management and duediligence tools, strategies, and configurable workflows; sponsor andinvestment profiles; fund search and filtering techniques; online andcollaborative access (e.g., via a local area network (LAN), wide areanetwork (WAN), and/or mobile communication); synchronized escrowmanagement; document digitization with document type recognitiontechnology, configurable payment flow (i.e., capital calls in anddistribution out); and access into/from third-party technologies (e.g.,via application programming interfaces (APIs)).

In various embodiments, the technology provides an online portal tosupport all or virtually all fund sponsors' and investors' privateplacement operations currently being performed manually, semi-manually,offline, or semi-offline. The described technology can also supplementonline transactions that require separate, often disconnected steps thatmay or may not occur over different communication means. For example, asponsor emails document A to an investor and then, after a random amountof time, the investor faxes executed document A and document B back tothe sponsor, who saves documents A and B to a computer folder to belater verified. The sponsor must separately review document B todetermine its type (e.g., a term agreement, a Form D that is a documentthat the SEC requires a company to file when it issues securities in aprivate placement under Regulation D, and/or a Private PlacementMemorandum (PPM)), whether any next steps are required (e.g., thesponsor must now obtain the sponsor's attorney's approval), and anyconsequences for the sponsor's and investor's workflow (e.g., document Cis no longer required because the investor sent document B; however,document Z may now be required).

UCEP generates, modifies and executes sponsor- and investor-specificprivate placement workflows, which, in one or more embodiments, areoperations, computations, strategies, goal/objective realizations, etc.,that are desired (e.g., by one or more sponsors/investors or industrynorms) and/or necessary (e.g., by government decree) for investing in afund. Non-limiting workflow examples include, in one or moreembodiments, verifying each party's compliance with and completion ofdocument requests; dynamically adding steps to a new or existingworkflow to conform with regulatory requirements (e.g., an investor maychange his/her profile such that new verification and/or documents arenecessary to prove that he/she is a “sophisticated” investor, etc.);verifying and linking to a third party (e.g., an investor's savingsaccount); generating reports; forecasting and determining per-investorreturn on investment (ROI); and creating and/or managing new workflows.Workflow operations are, in some embodiments, time-based; automaticallyand/or manually determined; triggered (e.g., in response to receivinginvestor approval, sending, via an encrypted network communication,forms A-D to one or more accountants); configured to move capitalbetween bank accounts and escrow accounts; and reusable for and acrossother investors/sponsors/funds/industries. UCEP generates workflows, invarious embodiments, based on investor profiles, sponsor profiles,sponsor and investor input, regulatory requirements, historicalinformation, industry information, and other private and publiclyavailable information, for example.

In one or more embodiments, UCEP technology receives information (e.g.,fund-related documentation, online/offline forms, documents, and otherdata) from sponsors, investors, and third parties. Information isreceived digitally (e.g., by being uploaded to a server, emailed, orshared from a third-party system, via File Transfer Protocol (FTP) orother data transfer means known in the art). UCEP analyzes the receivedinformation and, in one or more embodiments, is configured to determinethe nature/type of the information (e.g., regulatory, term agreement,etc.), any requests within the information (e.g., requests forsignatures, dates, Social Security number, bank account information,email addresses, spouse's name, checkboxes, etc.). UCEP generates and/orreferences a workflow (e.g., a series of steps and timing for completingfund investment) and determines where in the workflow to associate(e.g., via a database entry or other logical association) the receivedand/or requested information. For example, a term agreement may includea request (e.g., have a “blank” space) for an investor's name, bankaccount number, tax ID, signature, etc. UCEP can detect the request and,in some embodiments, automatically fill out requested information basedon, for example, data in a party's profile. Additionally oralternatively, UCEP is configured to prompt a party to enter missingdata via, e.g., a graphical user interface (GUI), email, Short MessageService (SMS) message or other means of notification, which can then beautomatically saved by UCEP and added to the party's profile, forexample.

UCEP provides an online portal for private placement investing. Invarious embodiments, UCEP shares and manages aggregated, digested, andsynthesized fund information that is provided by fund sponsors, providedby investors, and/or separately gathered by UCEP technologies (e.g.,UCEP can automatically retrieve public/private information from onlineresources, such as regulatory documents at government computers).Parties can access the information, via online capable technologies(e.g., computers, phones, tablets, etc.), to, for example, perform duediligence, review a fund's performance, and compare ROIs for differentfunds within the UCEP marketplace. Investors can directly invest, viaUCEP, in one or more funds, for example, at an agreed upon amount anddigitally execute any necessary documents to fulfill contractualobligations, all without leaving UCEP's online portal. In one or moreembodiments, UCEP provides investor tools for reviewing, e.g., a fund'sperformance reports, creating online portfolios of funds, and linkingexternal systems, such as third-party accounting programs (e.g.,Addepar) and/or investment accounts (e.g., Bank of America, Pensco, Rothaccount, IRA, etc.).

In one or more embodiments, UCEP technology automates private placementsbased on UCEP profiles. For example, UCEP can create, store, andmanipulate respective investor and sponsor profiles, which include someor all data required to complete investment documents. Profiles caninclude, in some embodiments, personal information (e.g., SocialSecurity information, spouse's name, bank/investment account numbers,third-party login/passwords, birthday, electronic signature storage,etc.), investment information (e.g., portfolios, investment strategy,ROIs, financial account information for processing a capital call,etc.), and other information (e.g., notification preferences,third-party software information, etc.). Profiles are used by UCEP for avariety of purposes, such as, e.g., automating document completion(e.g., filling out forms), applying electronic signatures,designing/suggesting investment strategies, generating personalizedROIs, etc.

UCEP, in one or more embodiments, can manage the delivery, notification,approval, and acknowledgement of documents to/from all parties. Forexample, when a document is available by UCEP (e.g., the document isuploaded or linked from a third-party account), UCEP technology, in someembodiments, sends one or more notification messages (e.g., email and/orSMS, etc.) to inform parties (e.g., investors) of the document'savailability. The party (e.g., investor), in response to receiving thenotification, can access UCEP to review and execute the document. ThenUCEP technologies can verify that the document was properly executed,update the party's (e.g., investor's) workflow (e.g., by sending a newdocument to the investor or to the sponsor), and/or notify the sponsor.

In various embodiments, UCEP can trigger a capital call and transfercapital from the investor's financial accounts (e.g., via one or morebank account numbers in the investor's profile) in response to detectingthat necessary documents were properly completed (e.g., the documentswere digitally signed via the investor's verified e-signature). Forexample, to facilitate or “facilitate and automate” automatic capitalcalls, UCEP can store (e.g., in a personalized profile) financialaccount information for the sender and the recipient of money, designatemultiple financial accounts for different purposes (e.g., two accountscan each be associated with one or more different financial accounts),manage electronic transfer of money between a sender (e.g., investor)and a recipient (e.g., sponsor or escrow company), communicate with theAutomated Clearing House (ACH) or other means for transmitting capital,and automatically initiate money transfer based on progression of a UCEPworkflow (e.g., some or all of the workflow's steps are detected by UCEPas being complete). In some embodiments, UCEP technologies combinedelivery of capital distribution and performance data. Harmonizeddistribution of funds and associated reporting simplifies an investor'smanagement of each of his or her private placement investments, which,in some instances, may have different and multiple types of capitaldistribution, such as real estate funds that may include each ofperiodic dividends, capital return, and appreciation, for example.

In various embodiments, UCEP is configured to automatically add, modify,and/or remove documents, procedures, information, and/or requests forinformation to UCEP associated storage (e.g., a database) and/or to aparty's profile, based on, for example, an investment type (e.g., a realestate fund versus bond fund), investor type (e.g., individual versusinstitutional investor), jurisdictional (e.g., domestic versus foreign),and/or other characteristic. For example, foreign investors investing inUnited States investments may have additional eligibility requirements,such as requiring additional withholdings and/or other informationrequired by various regulations (e.g., Office of Foreign Assets Control,the Patriot Act, the EB5 program, etc.). UCEP can determine from one ormore profile elements (e.g., a tax ID), that an investor is a non-U.S.(i.e., foreign) investor and, in response, request (e.g., via a GUI,SMS, or voice prompt) that the foreign investor fulfill additionalrequirements. In various embodiments, UCEP generates and/or modifiessteps within the foreign investor's workflow to obtain and manage therequested information. As another non-limiting example, a high net worth(“sophisticated”) investor may need to periodically prove by law his orher financial status (e.g., every three months). If the investor'sstatus changes such that the investor no longer qualifies as“sophisticated,” UCEP will request the investor to update his or herstatus to requalify before allowing the investor to proceed with othersteps required to invest into a private placement investment.

In one or more embodiments, UCEP provides APIs and/or other programmatictechniques for integrating with third-party software to, e.g., remotelyperform and/or request operations of the third-party software. Forexample, UCEP can integrate with other reporting services such asMercer, which is a company that provides advice and services duringvarious stages of the investment decision, risk management, andinvestment monitoring process. Mercer and/or similarorganizations/technologies can issue their own assessment reports thatare used by investors to determine the risk/reward of a particular fund,for example. UCEP can automate the process of requesting and receiving aMercer report, for example, all while the investor remains within theUCEP marketplace. For example, instead of a sponsor separatelycontacting and meeting with Mercer employees to establish a Merceraccount, uploading documents to Mercer servers, and signing variousagreements, etc., UCEP provides “single-click” access (and/or otherautomated technology) into Mercer, without requiring additional stepstraditionally required before UCEP technology. As a further example,UCEP can provide technology such as an indicator (e.g., an icon) withina GUI that, when selected by a sponsor and/or investor (e.g., via amouse, touch screen or other input device), causes UCEP to automaticallysend to Mercer some or all of the required data (e.g., data associatedwith a party's profile) to produce a Mercer report and, if someinformation is still required, prompt the party to enter the missingdata (e.g., via the UCEP's user interface or other input method). UCEPexchanges information with Mercer to facilitate the report's generationwithin Mercer and provide the completed Mercer report, via the UCEPmarketplace, to the sponsor and/or investor. Messages and/or requests,regardless of when issued from a third party (e.g., Mercer), can bedelivered to UCEP and then sent to a party's UCEP account for viewingoffline. Billing for third-party transactions, such as for a Mercerreport, can be integrated into UCEP's own billing system or directlybilled to the sponsor/investor.

UCEP, in various embodiments, includes criteria-based filtering andmatching for, e.g., viewing private placements within the marketplace.UCEP, as discussed above and further below, is a system of record forprivate placements and stores specific and generalized characteristicsthat are associated/tagged (e.g., linked via a database) for eachinvestment, sponsor, and potential/actual investor. Some characteristicsinclude a category or type of investment (real estate versus stocks),fund manager, amount of capital raised, fee structure, multi-unit versussingle-family real estate, risk profile, amount of debt, location ofinvestment, age of fund, the fund's/sponsor's goals, frequency ofpipeline updates, type/method of distribution (e.g., capitalappreciation versus income), fund manager's performance history, etc.Investors can apply filters (e.g., by manipulating a GUI or enteringkeyword text that is converted by UCEP into one or more specific searchqueries) to display investments having desired characteristics.Filtering can be narrowed or broadened by an investor to scale acrossthe entire marketplace of investments within the UCEP marketplace. Forexample, an investor may search for funds exceeding a certain ROI forresidential real estate investments of apartment buildings with 50+units in a desired geographic location. Additionally and/oralternatively, in some embodiments, filter-based searching is automatedby UCEP based on, for example, data within an investor's profile. Forexample, an automated UCEP search can include profile information (e.g.,based on learned habits, implications, investment history, or manuallyentered data) that forms the basis of a query that, when executed byUCEP, attempts to locate new and/or existing funds that meet theinvestor's unique profile.

In some embodiments, fund profiles can be saved and/or associated withan investor's new or existing investment portfolio. For example, aninvestor can add a fund to a “favorites” list to, e.g., further reviewor compare it to other funds that would be an alternate investmentopportunity or a comparable.

In one or more embodiments, UCEP includes aggregated portfolioforecasting. As described above, UCEP stores and/or has access tospecific capital call, distribution data, and performance metrics.Various UCEP technologies use some or all of this information toforecast future performance information, future capital calls, andfuture distribution information based on, e.g., funds' characteristics,as described above. For example, as a system of record for privateplacement funds, UCEP obtains rich data (e.g., from an investor,sponsor, third parties, reports, funds' performance history, publicinformation, etc.) on a per-fund basis for all funds within the UCEPmarketplace. Based on the rich data collected over the life of each fundwithin the marketplace, UCEP technology, in some embodiments,periodically generates metadata to determine, e.g., actual ROI andinvestment forecasts. The more funds within UCEP, the higher thefidelity of the metadata. As the corpus of metadata becomes richer, UCEPcan provide more accurate forecasts and ROIs based on, e.g.,performances of similar funds (i.e., funds having similarcharacteristics) within the UCEP marketplace. UCEP is configured todetermine and provide access to forecasts and projections as scores,reports, narratives, percentages, graphs and/or visualizations.

In some embodiments, metadata (and other information) is used by UCEP togenerate investor-specific private placement ROIs (“UCEP ROIs”) byanalyzing actual capital calls and distributions. Private placements, asmentioned above, are less regulated or unregulated by any centralauthority that could, in theory, verify fund performance informationprovided by fund managers. This lack of transparency can create fundintegrity concerns and increase the difficulty of determining aparticular investor's ROI from sponsor-reported ROIs, each of whichcould be an ROI averaged across multiple different investors anddifferent types of investors (e.g., individual high-wealth investorsversus a mutual fund), for example. As the central record authority forfunds within its marketplace, UCEP has access to rich metadata forcreating new metrics (e.g., unique ROIs) separate from, and incomparison to, generic (or misleading) metrics provided by fundmanagers. For example, a single fund may include hundreds of investorsof different types (e.g., mutual funds, institutional investors, privateinvestors, etc.); however, a fund manager may provide a single ROI forthe overall fund. As the “man in the middle” between fund sponsors andinvestors, UCEP is configured to collect information associated withpotentially each of the hundreds of investors. UCEP “knows”, forexample, the investor type, the investor's actual capital amount, theinvestor's actual distribution data (e.g., frequency and type ofdistribution), etc. In one or more embodiments, UCEP uses thisinformation to compute unique ROIs based on, for example, a specificinvestor or investor type. UCEP's independent verification of fundperformance injects authoritative trustworthiness into privateplacements and aids investors with up-to-date, actionable metadata formaking critical business decisions and, at the same time, reducing riskinherent in self-reporting or semi-self-reporting private funds.

The following description provides specific details for a thoroughunderstanding and enabling description of these embodiments. One skilledin the art will understand, however, that the described technology maybe practiced without many of these details. Additionally, somewell-known structures or functions may not be shown or described indetail, so as to avoid unnecessarily obscuring the relevant descriptionof the various embodiments.

Certain details are set forth in the following description and in FIGS.1-12 to provide a thorough understanding of various embodiments of thedisclosure. Other well-known structures and systems often associatedwith private placement investments have not been shown or described indetail below to avoid unnecessarily obscuring the descriptions of thevarious embodiments of the disclosure. Additionally, a person ofordinary skill in the relevant art will understand that the disclosuremay have additional embodiments that may be practiced without several ofthe details described below. In other instances, those of ordinary skillin the relevant art will appreciate that the methods and systemsdescribed can include additional details without departing from thespirit or scope of the disclosed embodiments.

Many of the details, dimensions, functions, and other features shown anddescribed in conjunction with the Figures are merely illustrative ofparticular embodiments of the disclosure. Accordingly, other embodimentscan have other details, dimensions, functions, and features withoutdeparting from the spirit or scope of the present disclosure. Inaddition, those of ordinary skill in the art will appreciate thatfurther embodiments of the disclosure can be practiced without severalof the details described below.

The terminology used in the description presented below is intended tobe interpreted in its broadest reasonable manner, even though it isbeing used in conjunction with a detailed description of certainspecific embodiments of the described technology. Certain terms may evenbe emphasized below; however, any terminology intended to be interpretedin any restricted manner will be overtly and specifically defined assuch in this Detailed Description section.

The techniques introduced below can be implemented by programmablecircuitry programmed or configured by software and/or firmware, orentirely by special-purpose circuitry, or in a combination of suchforms. Such special-purpose circuitry (if any) can be in the form of,for example, one or more application-specific integrated circuits(ASICs), programmable logic devices (PLDs), field-programmable gatearrays (FPGAs), etc.

FIGS. 1-2 and the following discussion provide a brief, generaldescription of a suitable computing environment in which aspects of thedescribed technology can be implemented. Although not required, aspectsof the described technology may be described herein in the generalcontext of computer-executable instructions, such as routines executedby a general- or special-purpose data processing device (e.g., a serveror client computer). Aspects of the described technology describedherein may be stored or distributed on tangible computer-readable media,including magnetically or optically readable computer discs, hard-wiredor preprogrammed chips (e.g., EEPROM semiconductor chips),nanotechnology memory, biological memory, or other data storage mediaknown or derived from future storage technology configurable to storecomputer instructions. Alternatively, computer-implemented instructions,data structures, screen displays, and other data related to thedescribed technology may be distributed over the Internet or over othernetworks (including wireless networks) on a propagated signal on apropagation medium (e.g., an electromagnetic wave, a sound wave, etc.)over a period of time. In some implementations, the data may be providedon any analog or digital network (packet-switched, circuit-switched, orother scheme).

The described technology can also be practiced in distributed computingenvironments where tasks or modules are performed by remote processingdevices, which are linked through a communications network, such as aLAN, a WAN, or the Internet. In a distributed computing environment,program modules or subroutines may be located in both local and remotememory storage devices. Those skilled in the relevant art will recognizethat portions of the described technology may reside on a servercomputer, while corresponding portions reside on a client computer(e.g., PC, mobile computer, tablet, or smart phone). Data structures andtransmission of data particular to aspects of the described technologyare also encompassed within the scope of the described technology.

Portions of the described technology can be practiced on and/ordistributed between one or more network appliances. A network applianceis a stand-alone device connected to a network and can be configured tocommunicate with another network appliance, server, and/or othercomputing device.

Referring to FIG. 1 , the described technology employs a computer 100,such as a personal computer or workstation, having one or moreprocessors 101 coupled to one or more user input devices 102 and datastorage devices 104. The computer 100 is also coupled to at least oneoutput device such as a display device 106 and one or more optionaladditional output devices 108 (e.g., printer, plotter, speakers, tactileor olfactory output devices, etc.). The computer 100 may be coupled toexternal computers, such as via an optional network connection 110, awireless transceiver 112, or both.

The input devices 102 may include a keyboard, a pointing device such asa mouse, and described technology for receiving human voice, touch,and/or sight (e.g., a microphone, a touch screen, and/or smart glasses).Other input devices are possible such as a joystick, pen, game pad,scanner, digital camera, video camera, and the like. The data storagedevices 104 may include any type of computer-readable media that canstore data accessible by the computer 100, such as magnetic hard andfloppy disk drives, optical disk drives, magnetic cassettes, tapedrives, flash memory cards, digital video disks (DVDs), Bernoullicartridges, RAMs, ROMs, smart cards, etc. Indeed, any medium for storingor transmitting computer-readable instructions and data may be employed,including a connection port to or node on a network, such as a LAN, WAN,or the Internet (not shown in FIG. 1 ).

Aspects of the described technology may be practiced in a variety ofother computing environments. For example, referring to FIG. 2 , adistributed computing environment with a network interface includes oneor more user computers 202 (e.g., mobile devices) in a system 200, eachof which includes a GUI program component (e.g., a thin clientcomponent, web browsers, etc.) 204 that permits the computer to accessand exchange data, such as network and/or security data, with a network206 such as a LAN or the Internet, including web sites, FTP sites, livefeeds, and data repositories within a portion of the network 206. Theuser computers 202 may be substantially similar to the computerdescribed above with respect to FIG. 1 . The user computers 202 may bepersonal computers (PCs) or mobile devices, such as laptops, mobilephones, or tablets. The user computers 202 may connect to the network206 wirelessly or through the use of a wired connection. Wirelessconnectivity may include any forms of wireless technology, such as aradio access technology used in wireless LANs or mobile standards suchas 2G/3G/4G/LTE. The user computers 202 may include other programcomponents, such as a filter component, an operating system, one or moreapplication programs (e.g., security applications, word processingapplications, spreadsheet applications, or Internet-enabledapplications), and the like. The user computers 202 may begeneral-purpose devices that can be programmed to run various types ofapplications, or they may be single-purpose devices optimized or limitedto a particular function or class of functions. More importantly, anyapplication program for providing a GUI to users may be employed, asdescribed in detail below. For example, a mobile application or “app”has been contemplated, such as one used in Apple's® iPhone® or iPad®products, Microsoft® products, Nokia® products, or Android®-basedproducts.

At least one server computer 208, coupled to the network 206, performssome or all of the functions for receiving, routing, and storing ofelectronic messages, such as security data, web pages, audio signals,electronic images, and/or other data. While the Internet is shown, aprivate network, such as an intranet, may be preferred in someapplications. The network may have a client-server architecture, inwhich a computer is dedicated to serving other client computers, or itmay have other architectures, such as a peer-to-peer, in which one ormore computers serve simultaneously as servers and clients. A databaseor databases 210, coupled to the server computer 208, store some content(e.g., security-related data) exchanged between the user computers 202;however, content may be stored in a flat or semi-structured file that islocal to or remote from the server computer 208. The server computer208, including the database(s), may employ security measures to inhibitmalicious attacks on the system and to preserve the integrity of themessages and data stored therein (e.g., firewall systems, secure socketlayers (SSL), password protection schemes, encryption, and the like).

The server computer 208 may include a server engine 212, one or more webmanagement components 214, a content management component 216, and adatabase management component 218. The server engine 212 performs basicprocessing and operating system level tasks. The web managementcomponent 214 handles creation, streaming, processing, and/or routing ofnetworking and/or security data. The web management component 214, invarious embodiments, includes technology for storing private placementdata and providing a private placement portal, described below. Usersmay access the server computer 208 by means of a network path associatedtherewith. The content management component 216 handles processes andtechnologies that support the collection, managing, and publishing ofprivate placement data, network data, and/or other data. The databasemanagement component 218 includes storage and retrieval tasks withrespect to the database, queries to the database, and storage of data.In some embodiments, multiple server computers 208, each having one ormore of the components 212-218, may be utilized. In general, the usercomputer 202 receives data input by the user and transmits such inputdata to the server computer 208. The server computer 208 then queriesthe database 210, retrieves requested pages, performs computations,and/or provides output data back to the user computer 202, typically forvisual display to the user.

FIG. 3 is a block diagram 300 of a unified compliance and executionplatform for private placements including several components and/orengines 302-326, such as an investor component 302, sponsor component304, portal component 310, fund component 312, document processingcomponent 314 (which may include document management and businessworkflow components), analysis component 316, due diligence component318, payment component 320, third-party component 322, and othercomponents/engines 326. UCEP provides a centralized, authoritative,collaborative, online workflow management marketplace for privateplacement investing. Investor component 302 gathers information frominvestors, such as login information, contact information, investmentobjectives, financial status, bank/savings/investment accounts, spouseinformation, notification preferences, and other information useful fordetermining an investor's preferences, investment strategies, portfolioholdings, investment history, and preferred/favorite funds and forcreating an investor profile. Sponsor component 304 is similar toinvestor component 302 and can include similar types of information.Sponsor component 304 can additionally include advertisement andmarketing information, sponsor information, and other information usefulfor providing to an investor. Portal component 310 provides technologyfor supporting an interface (e.g., a GUI) to a virtual space (e.g., awebserver-based system, database, mobile application, etc.) that hostsUCEP information and tools for sponsors and investors, such asworkflows, data repositories, report generators and viewers, andmanagement tools for uploading, downloading, and manipulating (e.g.,e-signing) documents, etc. Sponsors and investors can search the UCEPdatabase(s) for specific funds (e.g., based on one or more fundcharacteristics), update their profiles, and create/manipulateportfolios of funds, for example. Fund component 312, in variousembodiments, manages sponsor funds, including storing and hosting funddocumentation, storing/generating/managing fund workflow (e.g., whichdocuments are needed, their order for review/completion, timingconsiderations, notifications, etc.), and/or authenticating investors'access to fund information via, e.g., the portal component 310. Documentprocessing component 314 provides tools for manipulating and providingaccess to documents made available by investors or by sponsors orobtained by UCEP (e.g., UCEP technology can manually or automaticallydownload regulatory or other documents from online resources). Sometools provided by the document processing component 314 include documentupload, download, storage, securitization, retrieval, digitization, andmanipulation (e.g., reviewing, signing, highlighting, commenting,revising, or other means of document processing). Analysis component316, in various embodiments, processes, analyzes, compiles, sorts,compares, and evaluates fund information for determining general andinvestor-specific ROIs, generates reports (e.g., for comparing funds,ROIs, forecasting, etc.), and automatically selects and/or suggestsfunds that meet criteria of a sponsor's and/or investor's profile, forexample. Due diligence component 318 provides sponsors and investorswith access, via portal component 310, to fund data, information,profiles, marketing, and documentation for determining, e.g., whether ornot to invest into one or more funds. Payment component 320, in one ormore embodiments, accesses investors' (and sponsors') capital accountsfor, e.g., investing in one or more private placement funds. Forexample, payment component 320 can access investors' and sponsors'investment accounts, saving/checking accounts, IRAs, etc. fortransferring capital to UCEP, to an escrow account/agent, and/ordirectly to a sponsor's account for investing in funds and distributingcapital returns. Third-party component 322 provides access (e.g., viaAPIs) into software, systems, and platforms operated by third parties.For example, data can be sent from and to third-party accounting,reporting, project management, investment, and other products forintegrating into their technologies. Similarly, UCEP can pull data(e.g., via APIs) from third-party programs into UCEP for use by othercomponents 302-326, such as analysis component 316 (e.g., for generatingreports). Other components 326 are used by, available to, and/orprogrammable by UCEP/sponsors/investors.

FIGS. 4A-10 illustrate an example embodiment generated by, e.g., portalcomponent 310. By non-limiting example, FIGS. 4A-10 , in one or moreembodiments, depict an online portal, such as a website. To simplifyunderstanding of UCEP technology, FIGS. 4A-10 feature real estateprivate placement investments; however, funds may invest in any industryto create a multi-private placement investment marketplace.

FIG. 4A depicts an example login GUI 400 that is configured to allowsponsors and investors (or potential sponsors and/or investors)authorized access into the UCEP marketplace. Investors and sponsors canenter usernames 402 and passwords 404 for logging in 406 to the UCEPmarketplace. FIG. 4B shows an example GUI 420 implemented by UCEPtechnology for displaying various investor and/or sponsorcharacteristics 422, including but not limited to first name 424, lastname 426, email address 428, other information (not shown) 430 andinvestor/sponsor characteristics 432 that are submitted (e.g., viabutton 436) to UCEP for generating, e.g., one or more sponsor and/orinvestor profiles. For example, investor/sponsor characteristics 432display characteristics primarily for sponsors who might be wealthadvisors, pension funds or endowments, financial institutions or trustcompanies, real estate developers, or other types of industry sponsors;however, UCEP, in other embodiments, displays investor/sponsorcharacteristics for different types of investors (e.g., high-incomeinvestor, IRA investor, etc.). Optionally, a message 434 is provided tosend additional information to UCEP for creating a profile.

FIG. 5 illustrates an example user (e.g., sponsor or investor) dashboard500. In various embodiments, dashboard 500 is used by a user to navigateto various features implemented by UCEP and for displaying fundinformation display 508. Fund display 508 can display information (e.g.,fund advertisements, open/close fund information, portfolio status,ROIs, and/or other customizable information) automatically,periodically, and/or manually (e.g., by selecting indictors 510). Menubar 502 includes navigable menus for viewing sponsor/investorinformation 502 a, information regarding UCEP 502 b, marketplaceservices offered 502 c, education materials 502 d, interactive comments502 e, and contact information 502 f. Sponsor/investor information 502 aincludes navigable menus for accessing investor/sponsor-specificinformation 506, such as Strategies 506 a, Investing 506 b, Profiles 506c, Portfolio 506 d and Vault 506 e, each of which is further discussedbelow.

FIG. 6 depicts a non-limiting example of a strategy user interface 600that is one embodiment of a user interface displayed after thestrategies menu option 506 a of FIG. 5 is selected. Strategy userinterface 600 includes fund information 602 a-602 c, which is similar tofund information display 508 and which displays to sponsors and/orinvestors, for example, advertisements for funds seeking investment,UCEP-selected funds that match one or more characteristics in asponsor's and/or investor's profile, advertisements for funds seekinginvestment, etc. Strategy user interface 600, in various embodiments,includes a search engine 604 for searching for funds having one or morecharacteristics 606, such as a particular fund type (e.g., real estate),an open or closed fund, fund type subcategory (e.g., residential and/orcommercial real estate), jurisdiction/geography (e.g., domestic-,foreign-, state-based investments), and/or other characteristics (e.g.,ROI, capital raised, term, etc.) for categorizing funds.

FIGS. 7A-7H illustrate various embodiments for displaying investmentinformation after selecting Invest menu option 506 b. FIG. 7A depicts auser interface 700 that displays contact information 702 associated witha sponsor, e.g., based on the sponsor's profile or other information.FIG. 7B depicts a unified fund analysis interface 703 generated by UCEPto display fund-specific information (e.g., for the ABC HorizontalFund), including information derived from information and documentationreceived from fund sponsors. For example, in some embodiments, fundsponsors upload documents (e.g., PDFs, Google Docs, etc.) into theirprivate account within the UCEP marketplace. UCEP technology isconfigured to scan uploaded documents, perform character recognition,identify the document type (e.g., a prospectus) and its subsections,recognize portions of the documents that request investor feedback(e.g., signature blocks, approval indications, etc.), and act on thisinformation. In various embodiments, once information is recognized bythe technology, it is available for use by other aspects of thedescribed technology, such as profiles, search strategies, and makingrecommendations. Overview section 704 displays fund summary informationextracted from recognized information, and menu bar 706 displaysselectable menu options 706 a-706 g for displaying additionalinformation at, e.g., display section 710. For example, display section710 displays fund profile information when the profile menu option 706 ais selected. FIG. 7C is an example of a display of a fund's approach 712that is displayed by UCEP technology after the associated fund'sinformation is available (e.g., it is uploaded by a sponsor) and afterthe approach menu option 706 b is selected. Similarly, FIG. 7D is anexample of a fund's performance data 714 that is displayed when theperformance menu option 706 c is selected. FIG. 7E is an example of afund's management team 716 that is displayed by UCEP technology when theteam menu option 706 d is selected. FIG. 7F is an example of a fund'strending information 718 that is displayed by UCEP technology when thetrend menu option 706 e is selected. FIG. 7G is an example of a fund'sinvestment pipeline information 720 that is displayed by UCEP technologywhen the pipeline menu option 706 f is selected, and FIG. 7H is anexample of a fund's library of legal, marketing and due diligencematerials 722 that is displayed when the library menu option 706 g isselected.

Referring to FIG. 7H, a fund's library includes some or all of thedocuments (or links to the documents) necessary to research and investin a fund. Investors can access fund documents (e.g., by clicking onlinks associated with the documents), review the documents (e.g., viaUCEP document viewers), sign and date documents (e.g., via UCEP documentmanipulation tools), and submit to UCEP executed documents according toa workflow automatically determined by UCEP and/or configured bysponsors using, for example, one or more components 302-326 (e.g., thefund component 312). For example, an investor can access investmentdocuments 722 a by clicking respective links for, e.g., PrivatePlacement Memorandum, Subscription Agreement, Fund LLC Agreement, andForm of Promissory Note; can access marketing documents 722 b byselecting e.g., Fund Overview; and can access due diligence documents722 c, by selecting, e.g., Fund Overview, Manager Questionnaire,Financial Statements and Pipeline Opportunities. Each of the respectivetypes of documents 722 a-722 c, in some embodiments, is available forreview and execution (as necessary) without the investor leaving theUCEP marketplace (e.g., documents can be e-signed within UCEP). Invarious embodiments, one or more of each of the respective types ofdocuments 772 a-722 c are downloadable for review and execution and,subsequently, can be uploaded into UCEP, which will, for example, scan,categorize, and verify the documents and store them in one or more UCEPdata repositories. In one or more embodiments, when a document hascompleted one or more stages of a workflow (i.e., one or more steps ofreviewing, signing, and funding an investment), UCEP will notify theother party and proceed to the next step in the workflow (e.g.,verifying funds for sending to escrow).

FIGS. 8A-8G are non-limiting examples of a profile user interface 800when the profiles menu option 506 c is selected, for example. Profileuser interface 800 includes, for example, profile menu bar 805, investormenu 802 (or, alternatively, sponsor menu (not shown)) for modifyingexisting sponsor and investor profiles, and one or more links 804 forcreating new profiles. For example, in reference to FIGS. 8A-8B, whenthe investor menu option 805 a is selected, UCEP is configured todisplay and save 808 to its repositories account type profileinformation 806 a, regulatory profile information 806 b, and citizenshipinformation 806 c, for example. Other profile information (e.g.,preferred fund types, desired ROI, etc.) is contemplated by theinventors. FIG. 8C is another example of profile information requestedby UCEP, such as affiliation information 810 that is displayed when theaffiliations menu option 805 b is selected. FIG. 8D is an examplerequest of situation information 812 that is displayed when situationmenu option 805 c is selected. FIG. 8E is an example request of riskinformation 814 that is displayed when risk menu option 805 d isselected. FIG. 8F is an example request of experience information 816displayed when experience menu option 805 e is selected, and FIG. 8G isan example request of objectives information 818 displayed whenobjectives menu option 805 f is selected. Profile user interface 800, asreferred to in FIG. 8G, can also include other options, such as anoption 820 for requesting that UCEP analyze and generateinvestor-specific ROIs based on, for example, one or more types ofprofile information. For example, if option 820 is selected (e.g., by amouse), UCEP is configured to generate a UCEP ROI. The UCEP-generatedROI is, in one or more embodiments, based on a particular fund (e.g.,XYZ real estate fund) and one or more of the investor's profilecharacteristics. For example, UCEP can generate an ROI for investor Xbased on investor X being identified (via his/her profile) as having aninvestor type of high-value investors even if that fund only issuesgeneral ROIs (i.e., irrespective of the investor type, etc.).UCEP-generated ROIs are useful to an investor, at least because they canremove opacity and confusion around computing the actual ROI for aspecific investor in the fund.

FIGS. 9A-9B depict exemplary portfolio user interfaces 900 implementedby UCEP for viewing, via investor profile menu 902, investor- and/orfund-specific reports via report menu 904. For example, referring toFIG. 9B, UCEP can generate various types of reports (e.g., quarterlyreports 904 a-904 c, UCI ROI reports 904 n, etc.) by selecting one ofthe reports via report menu 904.

FIG. 10 depicts an example vault user interface 1000 for displayingindicators 1004 for accessing some or all fund documents for each fundin an respective investor's portfolio 1002. For example, in FIG. 10 , aninvestor's portfolio includes the Private Capital Management fund, AEIOUfund and BridgeHead fund, the documents of which are accessible (e.g.,by selecting the library links 1006) in respective libraries for eachfund, as described above.

FIG. 11 is a diagram of an exemplary investor data flow 1100 thatengages various components of the UCEP marketplace. In one or moreembodiments, data flow 1100 can be some or all of an investor's workflowfor investing in a fund. Data flow 1100 starts at step 1102, thenproceeds to the investor login step 1104, where an investor logs intohis/her account or sets up a new account in the marketplace. At step1106, the investor searches for funds that meet the investor's criteria(e.g., a real estate fund with a high ROI) and at step 1108 adds thatfund to the investor's portfolio or otherwise indicates an interest inthe portfolio (e.g., by associating the fund as a personal “favorite”).At step 1110, the investor decides whether or not to add any additionalfunds for potential investment. For example, more than one fund may meetthe investor's search criteria at step 1106 and, optionally, theinvestor can add this fund for further review. Additionally oralternatively, at step 1110, the investor may search for more funds byreturning to step 1106. When all funds are added for further review, atstep 1112, UCEP tools are provided for performing due diligence of eachadded fund. For example, UCEP tools can be engaged for reviewing,completing, and/or signing documents, as described above. At step 1116,UCEP determines whether all forms necessary to invest in at least one ofthe added funds have been completed by the investor (or the investor'sagents) and verified as accurate and complete. If, at step 1116, UCEPdetects that a document within a fund's workflow has not been properlycompleted (e.g., the investor has not completed all of the requiredblanks), the flow returns to step 1112. Otherwise, if one or more of theinvestor's capital accounts has not previously been linked (e.g., viaAPIs) to the investor's profile, at step 1118, UCEP establishescommunication to third-party capital accounts for investing in one ofthe funds. At step 1120, capital is transferred from one or more of thethird-party capital accounts into the UCEP marketplace (or, optionally,a separate escrow account or to the sponsor's designated capitalaccount), and the investor is now invested in the one or more funds. Thedata flow ends at step 1122. One or more steps of data flow 1100 are notrequired for investing in a fund. For example, if the investor does notneed to search UCEP for a fund (e.g., a fund was previously identifiedby the investor) and a capital account was previously linked (or theinvestor chooses to transfer money outside of UCEP), then steps1006-1010 and 1018 are not necessary for investing in a fund.

FIG. 12 is a diagram of an exemplary sponsor data flow 1200 that engagesvarious UCEP marketplace components 302-326. Specifically, sponsor dataflow 1200 describes various steps 1202-1226 for investing in a new fund.Some steps may be combined, and some steps are optional yet are shown toaid the reader in understanding various aspects of UCEP technology. Thesponsor data flow 1200 starts at step 1202 and then proceeds to step1204, where UCEP receives information for a new (or for modifying anexisting) fund. For example, a sponsor can create a fund by uploading orsending links to fund documentation and filling out forms provided byUCEP. At step 1206, fund documentation is processed. For example, UCEPcan analyze uploaded fund documentation to determine a document type(e.g., a prospectus, agreement, etc.); determine who needs to review thedocument (e.g., the investor and/or the investor's attorney, accountant,spouse, etc.); and identify what information is requested in thedocument (e.g., an investor's signature, account number, Social Securitynumber, etc.) based on identifying signature blocks, blank spaces, orother identifiers within a document. At step 1208, UCEP generates aprofile for the fund that determines the look and feel of thepresentation of the fund within the UCEP marketplace, associatescharacteristics with the fund (e.g., the fund is a commercialreal-estate fund investing in foreign multi-user apartment complexes, atech-startup fund focused on medical devices, or a fund managed by threesponsors with a history in residential real estate investing in Arizona,etc.), generates one or more workflows associated with an ordering ofsteps required to invest in the fund (e.g., an investor must completeeight forms; however, forms 4-5 must be completed at the same time whileform 7 must be completed only after forms 1 and 9 are executed).Workflows are adapted by UCEP to fit each individual investor based on,e.g., that investor's profile (and optionally the sponsor's profile).For example, a high-wealth individual may need to complete an extra form(e.g., to prove his/her wealth) that is not required by a mutual fund;therefore, UCEP will automatically create a step in the high-wealthindividual's workflow to request that the extra form be completed in anorder determined by the workflow. If the high-wealth individual is acitizen of a foreign country, as determined based on the investor'sprofile (for example), additional forms may be required and added to theforeign high-wealth investor's workflow. At step 1210, UCEP deliversand/or sends notification of available fund documents to a prospectiveinvestor. The investor can supply the requested information, the needfor which can be emphasized to the investor. For example, the investormay be informed by UCEP (e.g., by narrative and/or highlighting) to signpage 3 of a document and initial page 4, and/or UCEP will automaticallyfill out the requested information based on the investor's profile(e.g., UCEP will automatically fill in an investor's Social Securitynumber, account information, etc.). At step 1212, some or all of therequested documents are received, via UCEP, from the investor and, atstep 1214, it is determined whether the documents are accurate andcomplete. If the documents are not accurate or complete, a notificationand/or the requested document(s) are sent back to the investor at step1210. Otherwise, if the documents are verified as accurate and complete,at step 1216, UCEP will, in one or more embodiments, determine whetherany additional documents are required in an investor's workflow and, ifso, will return the flow to step 1210. When all documents necessary forinvesting in the fund have been received and verified as accurate andcomplete, at step 1218, UCEP, in some embodiments, is configured toreceive the investor's capital for investing in the fund (e.g., UCEP ora third party will escrow the capital) before the capital is ready to beinvested, at step 1220. In some embodiments, after investment of step1220, other actions are performed, such as receiving and/or sendingfinancial statements and investment reports and determineinvestor-specific ROIs (as described above). The flow 1200 ends at step1226, however, additional steps can be added and some are option (e.g.,steps 1222-1224). These steps, among other features of UCEP, provide acentralized authority that injects reliability, stability, andtransparency into the entire market of private placements.

Examples of the Unified Investment Management System

As described herein, in some embodiments, a unified investmentmanagement system facilitates the management, subscription, and/orpresentation of investments and associated information. The system,which may be included within UCEP 300 or include various components ofthe UCEP 300 described herein, generates, maintains, and utilizes aninvestment-based data structure or index, where each entry of the datastructure or index represents an investment managed by the system andincludes information relating various aspects of an investment (e.g.,fund, investor, and so on) with one another.

FIG. 13 is a block diagram illustrating various components of a unifiedinvestment management system 1300. The system 1300 includes functionalmodules or components that are implemented with a combination ofsoftware (e.g., executable instructions, or computer code) and hardware(e.g., at least a memory and processor). For example, the system 1300may include a data structure component 1310, a request component 1330, aquery component 1340, and an information component 1340.

In some embodiments, the data structure component 1310 is configuredand/or programmed to generate a data structure containing one or moreentries, wherein each of the one of more entries is associated with aninvestment. For example, the data structure component 1310 may generate,update, and/or modify a data structure or other data object, such as atable, index, or database of records that each represent an investment,such as an investment asset or vehicle.

The data structure, or index, therefore, may be a collection of tags(e.g., metadata) applied to the data objects stored by the system 1300.For example, given a collection of data objects, such as investor dataobjects, entity data objects, sponsor data objects, vehicle dataobjects, document data objects, workflow result data objects, and so on,the index may tag one or more of the different data objects with other,related, data objects. The index, therefore, may represent a relationaldatabase of tagged objects, where each object may be associated with atag to some or all of the other objects. In other words, the indexrelates the data as metadata to other data within the system.

The following is an example of a generated data structure or index ofinvestment data:

Result/ Investment ID Fund Investor Document Status Partners II KeyOffshore Jones Subscription1.pdf Signed Group Capital Fund Abbott,Offer.pdf Unsigned Benson Private three Startup Morris Compliance.pdfSigned Housing Dev Community Jones Offer.pdf unsigned

Therefore, the data structure relates various different types ofinformation associated with an investment, such as an investment sharedby many investors, a private a private placement investment, a realestate investment, and so on. Each entry of the data structure mayinclude some or all of the following information or data:

An identifier for the investment;

Information representative of a fund associated with the investment;

Information representative of a user associated with the investment;

Information or a link to one or more documents that represent a resultof business logic applied to the data (e.g., subscription logic resultof an investment between the fund associated with the investment and theuser associated with the investment);

Information or a link to a signature or acceptance documents associatedwith the investment;

Information identifying a current result or status of a workflowassociated with an investment or other related data (e.g., unsigneddocument, accepted terms, and so on);

Information associated with permissions, authorizations, or securityapplied to the data;

Information representing user-provided inputs or information (e.g.,electronic signature files, identification files or documents,verification files, user relationships, and so on; and/or otherinformation, tags, or metadata.

In some cases, the system may create additional records based on thedata within the data structure. For example, when updating an entityrecord, the system 1300 may retrieve an updated value after a businessprocess or workflow, update the index with the new value, and providethe new value to a record or document.

Thus, an entry in the data structure or index, for a given investment orvehicle, may include an identifier for the investment, the name of afund managing the investment, the name(s) of investors to the fund,information representing documents associated with the vehicle,information associated with workflows performed or currently beingperformed for the vehicle, information identifying statuses or resultsfor various processes of the workflows, and so on.

The investment-based data structure, therefore, may act as a queryabledata object, data structure, index, and/or relational database for thesystem 1300, enabling the system 1300 to quickly and efficiently manage,retrieve, obtain, and/or access data stored by the system 1300, andprovide the data to various workflows managed by the system 1300.

The system 1300 may receive and store the data from various sources. Forexample, the system 1300 may receive data input from users, fundmanagers, administrators, and so on, may extract data from documentsstored with the system 1300, may retrieve or access data from variousthird party services or entities, and so on.

In some embodiments, the request component 1320 is configured and/orprogrammed to receive a request (e.g., via a user interface provided bythe unified investment management system 1300) perform actionsassociated with stored data. As described herein, the actions may beactions to dynamically generate workflows, such as workflows that track,manage, and/or display information associated with investments managedby the unified investment management system 1300.

For example, the system 1300, via various selectable user interfaceelements (e.g., displayed menus, filters, buttons, and so on), mayreceive input from users associated with requests for information. Therequests may be associated with displaying certain types of information,rendering or publishing graphical data analyses, rendering or publishingdocuments associated with the investments (e.g., completion documents,subscription documents, compliance information, and so on), beginning orcompleting workflows, and so on. Further details regarding the differenttypes of user interfaces provided by the system 1300 are describedherein.

In some embodiments, the query component 1330 is configured and/orprogrammed to query the generated data structure or index to identifyinformation associated with the investments managed by the unifiedinvestment management system 1300, such as information that satisfies areceived request. The query component 1330 may query the informationstored in the data structure provided herein to identify one or moreinvestments and related information (e.g., tags or metadata) for certainquery terms and values. For example, a query using the terminvestor=Jones may provide results identifying the investments owned orheld by the investor named Jones, and/or the information related to thename Jones within the data structure.

The query component 1330, therefore, may query the entries of the datastructure to identify investments and/or other data tagged withinformation representative of the specific fund identified in thereceived request, investments tagged with information representative ofthe specific investor identified in the received request, workflowsassociated with the investment or tagged data, and so on.

In some embodiments, the workflow component 1340 is configured and/orprogrammed to dynamically generate or modify workflows associated withinvestments managed or tracked by the system 1300. The workflowcomponent 1340, for example, may render or publish various differentinterfaces resulting from workflows, such as fund interfaces thatpresent information satisfying the request, investor interfaces thatsatisfy the received request, and so on. The workflow component 1340,therefore, may cause the system 1300 to present a fund profile interfacethat displays investments managed by a specific fund, includinginformation tagged to the investments, an investor profile interfacethat displays investments held by a specific investor, includinginformation tagged to the investor, a management profile interface thatdisplays funds managed by a specific management company, includinginformation tagged to the management company, and so on.

As an example, the system accesses an index of information tagged to aspecific investor (e.g., metadata currently assigned or associated withthe investor), and renders an investor profile that includes a displaythat identifies the various associations or relationships between theinvestor and other data objects managed by the system 1300. The displaymay include, for example, funds owned by the investor, in progressworkflows that include the investor, and status information regardingcompliance documents stored by the system 1300 for the investor.

In addition, the workflow component 1340 may perform various actionsassociated with dynamically generating or modifying workflows, such asactions to generate or complete forms or documents, such as investmentsubscription forms, investment completion forms, signature forms,compliance forms, and so on. For example, the workflow component 1340may inject investment data into different logic algorithms to calculateinformation used to populate a digital document, such as a document thatrepresents a subscription to an investment by a potential investor, andstage or render the populated digital document for viewing via theinterface.

Thus, as described herein, by providing a specifically configured datastructure of investment information (such as a tagged index), the system1300 is capable of presenting various different views of informationassociated with the investments, regardless of the complexity ofrelationships between the parties and entities associated with theinvestments, among other benefits

FIG. 14 is a flow diagram illustrating a method 1400 for performingactions associated with investment data stored by the system 1300. Themethod 1400 may be performed by the system 1300 and, accordingly, isdescribed herein merely by way of reference thereto. It will beappreciated that the method 1400 may be performed on any suitablehardware.

In operation 1410, the system 1300 generates a data structure or indexcontaining one or more entries, where each of the one of more entries isassociated with an investment. For example, the generated datastructure, as described herein, may include entries that relate anidentifier for the investment, information representative of a fundassociated with the investment, information representative of a userassociated with the investment, information or a link to one or moredocuments that represent a subscription of the investment between thefund associated with the investment and the user associated with theinvestment, information or a link to a signature or acceptance documentsassociated with the investment; and/or other information, and so on.

In operation 1420, the system 1300 receives a request to perform anaction associated with investments managed by the unified investmentmanagement system 1300. For example, the system 1300, via variousselectable user interface elements (e.g., displayed menus, filters,buttons, and so on), may receive input from users associated withrequests for information or actions. The requests may be associated withdisplaying certain types of information, rendering or publishinggraphical data analyses, rendering or publishing documents associatedwith the investments (e.g., completion documents, subscriptiondocuments, compliance documents, and so on), starting or continuingworkflows related to producing records associated with investments, andso on.

In operation 1430, the system 1300 queries the generated data structureto identify information associated with the investments managed by theunified investment management system, such as for data that satisfies areceived request. For example, the query component 1330 query theentries of the data structure to identify investments tagged withinformation representative of the specific fund identified in thereceived request, investments tagged with information representative ofthe specific investor identified in the received request, and so on.

In operation 1440, the system 1300 performs an action using theidentified information, such as an action that presents the identifiedinformation that satisfies the received request, via one or moredynamically generated profiles based on metadata associated with thequery. For example, the workflow component 1340 may cause the system1300 to present a fund profile interface that displays investmentsmanaged by a specific fund, an investor profile interface that displaysinvestments held by a specific investor, a management profile interfacethat displays funds managed by a specific management company, and so on.

In some embodiments, as described herein, the system 1300 may utilizevarious logic algorithms (e.g., rules, applied formulas, routines, andso on) to determine values or other results as part of workflowoperations. For example, the system 1300 may obtain data associated witha statement for an investment (e.g., investor information and ownershippercentages), apply specific logic (e.g., a fee structure) and determinefees to be assigned to the various investors (or, fund balances). Thesystem 1300, therefore, stores various types of logic (e.g., capitalmanagement logic, allocation logic, fee logic, process management logic,and other business or calculation specific logic), which may be utilizedwhen completing various transactions, tasks, operations, and/or otherworkflow processes.

Therefore, the system 1300 provides users (e.g., investors, fundmanagers, and so on) with various profiles or views into a large amountof data associated with investments and various entities that own, hold,and/or manage the investments. Via the platform described herein, which,in some embodiments, obtains data (and various tagged relationships) tobe presented via the investment-based data structure, a user/manager maynavigate various profiles to view information associated withinvestments, search for new investments, populate and generatedocuments, store documents and other data, dynamically generate andmodify workflows, and so on. The following user interfaces illustratethe various types of profiles and other information that may bedisplayed or presented by the system 1300.

FIG. 15A is an example user interface 1500 of a fund profile, whichdisplays information associated with investment allocations for thefund. As described herein, the system 1300 may obtain the depictedinformation by querying the data structure with the name or anotheridentifier for the fund, and render the interface 1500 accordingly.

FIG. 15B is an example user interface 1510 of an investor profile, whichdisplays information associated with alternative investments held by theinvestor. As described herein, the system 1300 may obtain the depictedinformation by querying the data structure with the name or anotheridentifier for the investor, and render the interface 1510 accordingly.

FIG. 15C is an example user interface 1520 of an investment profile,which displays information associated with investors of a certaininvestment (e.g., a specific private placement investment). As describedherein, the system 1300 may obtain the depicted information by queryingthe data structure with the name or another identifier for the sponsorof the investment, and render the interface 1510 accordingly.

FIG. 15D is an example user interface 1530 of a manager profile, whichdisplays information associated with investment vehicles managed by acertain manager. As described herein, the system 1300 may obtain thedepicted information by querying the data structure with the name oranother identifier for the manager, and render the interface 1510accordingly.

FIG. 15E is an example user interface 1540 via which users may accessservice providers. As described herein, the system 1300 may obtain thedepicted information by obtaining information related in the datastructure to various investment vehicles and sponsors, and render theinterface 1510 accordingly.

FIG. 15F is an example user interface 1530 of active actions, or“to-dos,” managed by the system 1300. As described herein, the system1300 may obtain the depicted information by obtaining informationrelated in the data structure to a specific user, and render theinterface 1510 accordingly.

As described herein, the system 1300 may assist in various work flowsassociated with investor subscriptions of investments. FIGS. 16A-16F areexample user interfaces presented during completion of a subscription ofan investment.

For example, FIG. 16A is an example user interface 1600 via which a user(e.g., investor) may initiate a subscriber workflow. FIG. 16B is anexample user interface 1610 via which the system 1300, by querying thedata structure, manages compliance actions associated with investmentsubscriptions. FIG. 16C is an example user interface 1620 depicting thesystem 1300 populating a subscription form via data obtained oridentified via the data structure.

FIG. 16D is an example user interface 1630 depicting the system 1300rendering a legal document based on the populated subscription form.FIG. 16E is an example user interface 1640 depicting the system 1300sharing the rendered legal document with other parties managed by thesystem 1300. FIG. 16F is an example user interface 1650 depicting astatus of the investment subscription work flow.

Of course, the system 1300 may provide other user interfaces, such asinterfaces configured to display information managed by the system,interfaces configured to add or remove information, and so on. Forexample, FIG. 17A is an example user interface 1700 depicting amanagement company profile that displays information associated withdifferent managed funds. As another example, FIG. 17B is an example userinterface 1710 via which a user may select an investment vehicle andview detailed information about the investment and relationships toinvestors, managers, and so on. FIG. 17C is an example user interface1720 via which a user may select an investor and view detailedinformation about the investor and his/her relationships with variousinvestment vehicles.

FIG. 18A is an example user interface 1800 depicting the contents of adocument vault managed by the system 1300. As depicted, via the datastructure described herein, the system 1300 may identify, obtain, andpresent information for each of the stored documents, such as the fundassociated with the document, the investor associated with the document,the date/time when the documents was generated or completed, and so on.In some cases, the user interface may stage or provide preview versionsor displays of documents or information before or during the completionof document uploads.

FIG. 18B is an example user interface 1810 depicting an upload interfacethat facilitates the uploading of documents to the document vaultmanaged by the system 1300. As depicted, the user interface 1810provides user-selectable elements configured to tag documents withmetadata. These elements, or tools, may facilitate bulk-tagging ofdocuments, individual tagging of documents, and so on. Once tagged, thedocuments, metadata, and associated investment data may be added to thedata structures described herein.

For example, when a document is stored or uploaded to the data vault(via various upload mechanisms), the system 1300 may tag the documentwith various metadata associated with the document, such as metadataassociated with an entity, sponsor, vehicle, document, workflow result,and so on. The system 1300 may then identify, sort, filter, and/or finddocuments via the tagged metadata.

Therefore, in some embodiments, the system 1300 creates and maintains adata structure or other data object for all investments managed by thesystem 1300. The data structure includes an entry for each investmentunder management, where each entry includes an identifier for theinvestment, information representative of a fund associated with theinvestment, information representative of a user associated with theinvestment, and other related information. Using the data structure, thesystem 1300 is capable of quickly and efficiently rendering variousdifferent profile views of the large amounts of data managed by thesystem, such as fund profiles, investor profiles, and so on.

Use Cases for the Unified Investment Management System

As described herein, the unified investment management system 1300maintains alternative investment data in various indexed relationships,and performs various actions associated with the indexed data, such asworkflow steps or processes that would be too cumbersome or inefficientto perform without the indexed data, among other benefits

For example, the following workflows may perform operations usingindexed data:

Capital Statement generation, where investor information and fundperformance information is obtained and presented via one or more views.For example, the workflows may utilize the data when automaticallygenerating capital statements (e.g., including commentary) anddistributing (e.g., a mail merge of unique investor specific informationwith overall fund performance information), staging, and/or displayingthe statements;

Investment tracking, where an investment may be tracked and managed fromthe initial identification of potential investors (e.g., via prospectprofiles that identify investors, probability of investments, potentialinvestment amounts, and so on) for a fund of vehicle, the variousworkflows associated with generating records for a completed investmenttransaction, the performance of the investment, compliance ormaintenance information, and so on;

Compliance records generation, such as information useful to an investorfor providing fiduciary oversight and related information;

Private Placement Investment management, where the workflows (asdescribed herein) may initiate a capital call from a financial account(with or without approval), based on the completion of a documentsigning;

Capital Call and Distribution Processes, where the system 1300 storesthe financial account information for the sender and recipient of money;enables either party to update their financial account informationand/or designate multiple accounts for different purposes; manages thebusiness logic and workflow for money movement from the sender torecipient; utilizes ACH or other methods to transmit the money;initiates money movement based on the completion of capital calls,streamlines interactions with foreign investors; and so on;

Audit Processes, where the system 1300 stores historical log/audit trailinformation (e.g., information involving pre-financing interactions, duediligence review, compliance, and so on) that tracks theinvestor/manager/user access of data by viewing, editing, downloading,and so on, within the system 1300. The system, therefore, may utilizethe related data to review data, metadata and logic, date stamps, userinteractions (locations and time periods) within the system, compliancedates, reporting dates, and other information, events, or actions; andso on.

In some embodiments, the system 1300 may forecast future performance andcash flows for investments, vehicles, funds, and other data objects. Thesystem 1300 may utilize stored information to forecast future resultsgiven past results; forecast results at fund levels; forecast events atfund and investor levels, forecast events at group of fundslevels/aggregated levels, determine recommendations for targetmarket/investors based on tracked or determined benchmarks (e.g., age,location, strategy, investor type, historical occurrences, and so on).

For example, the system 1300 may perform aggregated portfolioforecasting, where the data relationships generated and maintained bythe system 1300 include specific capital call and distribution data andperformance data. Using the data, the system 1300 may forecast and/orpresent performance information based on the storage of specific andgeneral characteristics for private placement investments, and/orforecast and/or present future capital call and distribution informationbased on the storage of specific and general characteristics for privateplacement investments, among other information.

In some embodiments, the system 1300 may collaborate, integrate, orexchange information with various third party systems, such as fundaccounting systems. The collaboration may facilitate the storage andaccess to performance data/reports, the delivery performance reportingdata/reports along with the related distributions as described herein,the delivery of performance reporting data/reports to third partyreporting systems (e.g., Adepar, Advent/Blackdiamond, and so on). Thedelivery may be via manual processes, export, email, APIs, systemintegrations, and so on.

For example, the system 1300 facilitates the exchange or sharing ofinvestment opportunities via third party marketplaces that provideinvestments available to various audiences, such as crowd fund groups,institutional investors, and so on. In some cases, the third partysystems may utilize various components or processes described herein,such as transactions, investments, compliance processes, and so on.

In order to exchange information, the system 1300, in some embodiments,publishes and/or provides APIs, which provide third party systems withaccess to data, processes, workflows, and so on, provided by the system.Via the APIs, the system 1300 enables data to be imported from orexported to third parties, which may speed up, increase the accuracy of,and/or increase the scope of various reporting processes of financialdata, performance data, compliance data, and so on.

APIs may also facilitate third party partnerships, which may enableinvestment approval by certain financial platforms, enable investment byapproved third parties (e.g., service providers, authorized users, andso on), sharing of data or documents with approved third parties, and soon. The system 1300, therefore, may act to manage or provide data tomany different parties internal and/or external to the system 1300.

Examples of User Experience Functions of the Unified InvestmentManagement System

In some cases, the system 1300, via various user interfaces, may providenotifications to users. The notifications may include: alerts associatedwith workflow activities, alerts associated with investment events,alerts associated with changes or modifications to documents orworkflows, and so on.

Additionally, the system 1300 may provide various communicationmechanisms to facilitate the exchange (e.g., internal to the system1300) between investors and/or fund managers. Example mechanisms mayinclude chat boxes, notation or annotation recording, emails, instantmessaging, voice communications, document sharing, and so on. Asdescribed herein, the system may tag any or all recorded messages orcommunications to the various associated entities, and record the tagsin the indexes described herein. Thus, in some embodiments, the system1300 described herein manages investment data, such as data associatedwith alternative investments, via one or more indexes or other datastructures that maintain relationships between various data objects. Viathese data relationships, the system 1300 may generate or provideinformation to workflows (which may generate documents or records),render and present various profiles of information, and so on.

CONCLUSION

In general, the detailed description of embodiments of the describedtechnology is not intended to be exhaustive or to limit the describedtechnology to the precise form disclosed above. While specificembodiments of, and examples for, the described technology are describedabove for illustrative purposes, various equivalent modifications arepossible within the scope of the described technology, as those skilledin the relevant art will recognize. For example, while processes orblocks are presented in a given order, alternative embodiments mayperform routines having steps, or employ systems having blocks, in adifferent order, and some processes or blocks may be deleted, moved,added, subdivided, combined, and/or modified. Each of these processes orblocks may be implemented in a variety of different ways. Also, whileprocesses or blocks are at times shown as being performed in series,these processes or blocks may instead be performed in parallel, or maybe performed at different times.

The teachings of the described technology provided herein can be appliedto other systems, not necessarily the system described herein. Theelements and acts of the various embodiments described herein can becombined to provide further embodiments.

The techniques introduced above can be implemented by programmablecircuitry programmed or configured by software and/or firmware, orentirely by special-purpose circuitry, or in a combination of suchforms. Such special-purpose circuitry (if any) can be in the form of,for example, one or more application-specific integrated circuits(ASICs), programmable logic devices (PLDs), field-programmable gatearrays (FPGAs), etc.

Software or firmware for implementing the techniques introduced here maybe stored on a machine-readable storage medium and may be executed byone or more general-purpose or special-purpose programmablemicroprocessors. A “machine-readable storage medium,” as the term isused herein, includes any mechanism that can store information in a formaccessible by a machine (a machine may be, for example, a computer,network device, cellular phone, personal digital assistant (PDA),manufacturing tool, any device with one or more processors, etc.). Forexample, a machine-accessible medium includes recordable/non-recordablemedia (e.g., read-only memory (ROM); random access memory (RAM);magnetic disk storage media; optical storage media; flash memorydevices; etc.

The term “logic” and “components” as used herein, can include, forexample, special-purpose hardwired circuitry, software, and/or firmwarein conjunction with programmable circuitry, or a combination thereof.

These and other changes can be made to the described technology in lightof the above Detailed Description. While the above description detailscertain embodiments of the described technology and describes the bestmode contemplated, no matter how detailed the above appears in text, thedescribed technology can be practiced in many ways. The describedtechnology may vary considerably in its implementation details, whilestill being encompassed by the described technology disclosed herein. Asnoted above, particular terminology used when describing certainfeatures or aspects of the described technology should not be taken toimply that the terminology is being redefined herein to be restricted toany specific characteristics, features, or aspects of the describedtechnology with which that terminology is associated. In general, theterms used in the following claims should not be construed to limit thedescribed technology to the specific embodiments disclosed in thespecification, unless the above Detailed Description section explicitlydefines such terms. Accordingly, the actual scope of the describedtechnology encompasses not only the disclosed embodiments but also allequivalent ways of practicing or implementing the described technology.

To reduce the number of claims, certain aspects of the describedtechnology are presented below in certain claim forms, but the applicantcontemplates the various aspects of the described technology in anynumber of claim forms. For example, while only one aspect of thedescribed technology is recited as a means-plus-function claim under 35U.S.C. § 112, ¶6, other aspects may likewise be embodied as ameans-plus-function claim, or in other forms, such as being embodied ina computer-readable medium. (Any claims intended to be treated under 35U.S.C. § 112, ¶6 will begin with the words “means for,” but use of theterm “for” in any other context is not intended to invoke treatmentunder 35 U.S.C. § 112, ¶6.) Accordingly, the applicant reserves theright to pursue additional claims after filing this application topursue such additional claim forms, in either this application or in acontinuing application.

We claim:
 1. A workflow data management system for verifying compliance to workflows, comprising: a memory; and at least one processor configured to perform steps comprising: receiving information via a first graphical user interface, the information comprising a request, the request comprising a user's information associated with a user; generating a workflow in an investment management system or a fund management system, wherein the workflow is associated with a set of documents and is based on the request; receiving a data object generated by the workflow, wherein the data object is associated with an investment; creating one or more records within a data structure based on the data object; querying the data structure to identify a tag associated with the data object based on the request, wherein the data structure comprises a collection of tags associated with respective data objects stored in the data structure; providing, to the workflow, information indicative of relationships between the data objects stored in the data structure based on the collection of tags; determining, based on the tag, a related data object comprising at least one of a progress workflow associated with an investor of the investment, a fund owned by the investor, and a compliance document; selecting a document of the set of documents based on the request, the information indicative of relationships between the data objects, and the related data object, wherein the selected document needs to be executed by the user; automatically populating the selected document with data comprising the one or more records; providing, via a second graphical user interface, the populated document; calculating, based on the user's information, the request, and the related data object, a return on investment for the user; receiving, via the second graphical user interface, a completed version of the populated document; performing character recognition on the completed version of the populated document to verify that the user properly completed the populated document; based upon determining that the completed version of the populated document lacks required information, prompting a party to enter missing data; and upon determining that the completed version of the populated document is properly completed, initiating money transfer based on progression of the workflow.
 2. The system of claim 1, wherein the steps further comprise querying the data structure based on a filter associated with the request.
 3. The system of claim 1, wherein the request comprises a document uploaded via the first graphical user interface.
 4. The system of claim 3, wherein the steps further comprise: rendering an input interface configured to receive tags input by the user and associated with the document; and associating the one or more generated record with the document and the received tags.
 5. The system of claim 1, wherein the steps further comprise populating the document with metadata associated with the one or more data records.
 6. A computer-implemented method for verifying compliance to workflows, the method comprising: receiving information via a first graphical user interface, the information comprising a request, the request comprising a user's information associated with a user; generating a workflow in an investment management system or a fund management system, wherein the workflow is associated with a set of documents and is based on the request; receiving a data object generated by the workflow, wherein the data object is associated with an investment; creating one or more records within a data structure based on the data object; querying the data structure to identify a tag associated with the data object based on the request, wherein the data structure comprises a collection of tags associated with respective data objects stored in the data structure; providing, to the workflow, information indicative of relationships between the data objects stored in the data structure based on the collection of tags; determining, based on the tag, a related data object comprising at least one of a progress workflow associated with an investor of the investment, a fund owned by the investor, and a compliance document; selecting a document of the set of documents based on the request, the information indicative of relationships between the data objects, and the related data object, wherein the selected document needs to be completed by the user; automatically populating the selected document with data comprising the one or more records; providing, via a second graphical user interface, the populated document; calculating, based on the user's information, the request, and the related data object, a return on investment for the user; receiving, via the second graphical user interface, a completed version of the populated document; performing character recognition on the completed version of the populated document to verify that the user properly completed the populated document; upon determining that the completed version of the populated document lacks required information, prompting a party to enter missing data; and upon determining that the completed version of the populated document is properly completed, initiating money transfer based on progression of the workflow.
 7. The system of claim 6, wherein the steps further compromise querying the data structure based on a filter associated with the request.
 8. The method of claim 6, wherein the request comprises a document uploaded via the first graphical user interface.
 9. The method of claim 8, wherein the method further comprises: rendering an input interface configured to receive tags input by the user and associated with the document; and associating the one or more generated record with the document and the received tags.
 10. The method of claim 6, wherein the method further comprises populating the document with metadata associated with the one or more data records.
 11. A non-transitory computer-readable storage medium storing instructions executable by one or more processors to cause the one or more processors to perform operations comprising: receiving information via a first graphical user interface, the information comprising a request, the request comprising a user's information associated with a user; generating a workflow in an investment management system or a fund management system, wherein the workflow is associated with a set of documents and is based on the request; receiving a data object generated by the workflow, wherein the data object is associated with an investment; creating one or more records within a data structure based on the data object; querying the data structure to identify a tag associated with the data object based on the request, wherein the data structure comprises a collection of tags associated with respective data objects stored in the data structure; providing, to the workflow, information indicative of relationships between the data objects stored in the data structure based on the collection of tags; determining, based on the tag, a related data object comprising at least one of a progress workflow associated with an investor of the investment, a fund owned by the investor, and a compliance document; selecting a document of the set of documents based on the request, the information indicative of relationships between the data objects, and the related data object, wherein the selected document needs to be completed by the user; automatically populating the selected document with data comprising the one or more records; providing, via a second graphical user interface, the populated document; calculating, based on the user's information, the request, and the related data object, a return on investment for the user; receiving, via the second graphical user interface, a completed version of the populated document; performing character recognition on the completed version of the populated document to verify that the user properly completed the populated document; upon determining that the completed version of the populated document lacks required information, prompting a party to enter missing data; and upon determining that the completed version of the populated document is properly completed, initiating money transfer based on progression of the workflow.
 12. The system of claim 11, wherein the steps further compromise querying the data structure based on a filter associated with the request.
 13. The storage medium of claim 11, wherein the request comprises a document uploaded via the first graphical user interface.
 14. The storage medium of claim 13, wherein the operations further comprise: rendering an input interface configured to receive tags input by the user and associated with the document; and associating the one or more generated record with the document and the received tags.
 15. The system of claim 1 wherein the steps further comprise: determining the workflow based on at least one of: account type information associated with the user, regulatory profile information associated with the user, or citizenship information associated with the user.
 16. A workflow data management system for verifying compliance to workflows, the system comprising: a memory; and at least one processor configured to perform steps comprising: receiving information via a first graphical user interface, the information comprising a request, the request comprising a user's information associated with a user; generating a workflow associated with a set of documents and is based on the request; receiving a data object generated by the workflow; creating one or more records within a data structure based on the data object; querying the data structure to identify a tag associated with the data object based on the request, wherein the data structure comprises a collection of tags associated with respective data objects stored in the data structure; providing, to the workflow, information indicative of relationships between the data objects stored in the data structure based on the collection of tags; determining, based on the tag, a related data object comprising at least one of a progress workflow associated with a compliance document; selecting a document of the set of documents based on the request, the information indicative of relationships between the data objects, and the related data object, wherein the selected document needs to be executed by the user; automatically populating the selected document with data comprising the one or more records; providing, via a second graphical user interface, the populated document; receiving, via the second graphical user interface, a completed version of the populated document; performing character recognition on the completed version of the populated document to verify that the user properly completed the populated document; based upon determining that the completed version of the populated document lacks required information, prompting a party to enter missing data; and upon determining that the completed version of the populated document is properly completed, initiating an action according to the workflow. 